|
Many software bugs are merely annoying or inconvenient but some can have extremely serious consequences – either financially or as a threat to human well-being. The following is a list of software bugs with significant consequences: == Space exploration == * A booster went off course during launch, resulting in the destruction of NASA Mariner 1. This was the result of the failure of a transcriber to notice an overbar in a written specification for the guidance program, resulting in the coding of an incorrect formula in its FORTRAN software. (July 22, 1962).〔(【引用サイトリンク】 Space FAQ 08/13 – Planetary Probe History )〕 Note that the initial reporting of the cause of this bug was incorrect.〔 in , reprinted in . See (Risks Digest: ''Mariner 1'', Vol. 9: Iss. 54, 12 Dec 89 ) (and (【引用サイトリンク】 Mariner I -- no holds BARred )〕 * The Russian Space Research Institute's Phobos 1 (Phobos program) deactivated its attitude thrusters and could no longer properly orient its solar arrays or communicate with Earth, eventually depleting its batteries. (September 10, 1988). * The European Space Agency's Ariane 5 Flight 501 was destroyed 40 seconds after takeoff (June 4, 1996). The US$1 billion prototype rocket self-destructed due to a bug in the on-board guidance software. * In 1997, the Mars Pathfinder mission was jeopardised by a bug in concurrent software shortly after the rover landed, which was found in preflight testing but given a low priority as it only occurred in certain unanticipated heavy-load conditions.〔Parallel sparking: Many chips make light work, Douglas Heaven, New Scientist magazine, issue 2930, 19 August 2013, p44. (Online (by subscription) )〕 The problem, which was identified and corrected from Earth, was due to computer resets caused by priority inversion.〔(What Really Happened on Mars ) by Glenn Reeves of the JPL Pathfinder team〕〔(Explanation of priority inversion problem experienced by Mars Pathfinder )〕 * The European Space Agency's CryoSat-1 satellite was lost in a launch failure in 2005 due to a missing shutdown command in the flight control system of its Rokot carrier rocket. * NASA Mars Polar Lander was destroyed because its flight software mistook vibrations due to atmospheric turbulence for evidence that the vehicle had landed and shut off the engines 40 meters from the Martian surface (December 3, 1999).〔(【引用サイトリンク】 title=Mars Polar Lander )〕 * * Its sister spacecraft Mars Climate Orbiter was also destroyed, due to software on the ground generating commands in pound-force (lbf), while the orbiter expected newtons (N). * A mis-sent command from Earth caused the software of the NASA Mars Global Surveyor to incorrectly assume that a motor had failed, causing it to point one of its batteries at the sun. This caused the battery to overheat (November 2, 2006).〔(【引用サイトリンク】 Report Reveals Likely Causes of Mars Spacecraft Loss )〕〔(【引用サイトリンク】 Faulty Software May Have Doomed Mars Orbiter ) 〕 * NASA's ''Spirit'' rover became unresponsive on January 21, 2004, a few weeks after landing on Mars. Engineers found that too many files had accumulated in the rover's flash memory. It was restored to working condition after deleting unnecessary files.〔(【引用サイトリンク】title=Out of memory problem caused Mars rover's glitch )〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「List of software bugs」の詳細全文を読む スポンサード リンク
|